Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@Prezel/build-logic/convention/src/main/java/com/team/prezel/buildlogic/convention/plugin/AndroidFeatureImplConventionPlugin.kt`:
- Line 28: Remove the Timber dependency line in
AndroidFeatureImplConventionPlugin.kt (the
"implementation"(libs.findLibrary("timber").get()) entry) from the shared
convention and instead add an implementation dependency for Timber in the
profile feature's build.gradle.kts (the profile module's implementation
configuration). This keeps Timber only in the ProfileImpl module and prevents
other feature-impl modules (history, home, login, my, splash) from getting an
unnecessary dependency.

In `@Prezel/core/ui/src/main/java/com/team/prezel/core/ui/AdvancedImePadding.kt`:
- Around line 21-22: The compute for consumePadding in AdvancedImePadding.kt is
wrong: replace coordinates.positionInWindow() with coordinates.positionInRoot()
to use root-relative coordinates, and apply coerceAtLeast(0) to the entire
subtraction result (i.e., (rootSize.height - (positionInRoot().y +
size.height)).toInt().coerceAtLeast(0)) so negative paddings are clamped; update
the identical calculation at the other occurrence (the second consumePadding
usage) to the same pattern referencing findRootCoordinates(), positionInRoot(),
size, and coerceAtLeast.

In
`@Prezel/feature/login/impl/src/main/java/com/team/prezel/feature/login/impl/landing/LoginViewModel.kt`:
- Around line 58-63: In fetchMyInfo() the local flag isProfileCreateComplete is
hardcoded true which forces NavigateToHome; change this to use the actual user
registration/profile-completion value (or at minimum default to false) instead
of true so new users can reach the profile creation flow—update the logic inside
LoginViewModel.fetchMyInfo() to read the real completion state (or set
isProfileCreateComplete = false) and then call
sendEffect(LoginUiEffect.NavigateToHome) or
sendEffect(LoginUiEffect.NavigateToTerms) based on that value.

In
`@Prezel/feature/my/impl/src/main/java/com/team/prezel/feature/my/impl/MyScreen.kt`:
- Line 16: The hardcoded Text("My") in MyScreen should be replaced with a string
resource; change the Text call to use stringResource(R.string.my_title) (import
androidx.compose.ui.res.stringResource) so the UI text comes from resources, and
add the key my_title with value "My" to your strings.xml resource file.

In
`@Prezel/feature/my/impl/src/main/java/com/team/prezel/feature/my/impl/MyUiState.kt`:
- Around line 3-7: MyUiState currently only defines Loading and LoadFailed so it
cannot represent a successful (loaded) state; add a Success variant to the
sealed interface (e.g., data class Success(val data: <payloadType>) : MyUiState)
so MyViewModel/MyScreen can switch on MyUiState for the loaded content instead
of using separate flags; update any code referencing MyUiState to handle
Loading, Success and LoadFailed accordingly and choose an appropriate payload
type name for your feature's data.

In
`@Prezel/feature/profile/impl/src/main/java/com/team/prezel/feature/profile/impl/contract/ProfileUiState.kt`:
- Around line 55-57: The current submitButtonEnabled logic allows submission
when only profileImage changed even if nickname is invalid; change it so that if
nickname was modified (nickname != originalNickname) the button is enabled only
when nicknameValidation == NicknameValidationState.Available, otherwise
(nickname unchanged) enable the button when profileImage !=
originalProfileImage; update the submitButtonEnabled computation (referencing
submitButtonEnabled, nickname, originalNickname, nicknameValidation,
NicknameValidationState.Available, profileImage, originalProfileImage) to
implement this conditional branching.

In
`@Prezel/feature/profile/impl/src/main/java/com/team/prezel/feature/profile/impl/ProfileViewModel.kt`:
- Around line 120-123: 현재 닉네임 검증 결과가 오래된 입력에 덮어쓰는 문제를 방지하려면 updateState 블록 안에서
fetchedState.updateProfile(...)을 호출하기 전에 검증 대상 닉네임이 현재 UI 상태의 nickname과 일치하는지
확인하도록 변경하세요; 즉, ProfileUiState.Fetched에서 가져온 fetchedState.nickname과
validationState(현재 변수명)의 검증 대상(예: validationState.input 또는
validationState.nickname)에 대해 equality 체크를 하고 다르면 기존 currentState를 반환하여 무시하도록
처리한 뒤, 같을 때만 fetchedState.updateProfile(nicknameValidation = validationState)을
호출하도록 수정하세요.
- Around line 133-150: submitProfile currently always sends
ProfileUiEffect.NavigateToHome even when editing; change it to branch on the
runtime type of fetchedState (ProfileUiState.Create vs ProfileUiState.Edit) and
send the appropriate effect (NavigateToHome for Create, OnBack for Edit) using
sendEffect, and when re-enabling the patchUserProfileUseCase callback ensure the
success handler uses the same branching logic (refer to submitProfile,
ProfileUiState.Fetched, ProfileUiState.Create, ProfileUiState.Edit,
ProfileUiEffect.NavigateToHome, ProfileUiEffect.OnBack, and sendEffect).

---

Nitpick comments:
In
`@Prezel/core/designsystem/src/main/java/com/team/prezel/core/designsystem/component/PrezelAvatar.kt`:
- Line 33: The component default was changed to PrezelAvatarSize.REGULAR which
will silently enlarge every caller that omitted size; revert the parameter
default in the PrezelAvatar constructor signature from PrezelAvatarSize.REGULAR
back to the original smaller default (e.g. PrezelAvatarSize.SMALL) so existing
callers keep their intended size, and for screens that need the larger 120dp
explicitly update the call sites to pass size = PrezelAvatarSize.REGULAR; update
references to PrezelAvatar and PrezelAvatarSize accordingly.

In
`@Prezel/feature/profile/impl/src/main/java/com/team/prezel/feature/profile/impl/navigation/ProfileEntryBuilder.kt`:
- Around line 16-32: Extract the duplicated ProfileScreen construction used in
entry<ProfileNavKey.Create> and entry<ProfileNavKey.Edit> into a single reusable
function or lambda (e.g., a private function that takes the LocalNavigator or
returns the composable content) and call that from both entries; move the
LocalNavigator.current retrieval into the shared function or accept it as a
parameter so navigateToHome and onBack closures are created once and reused by
both entry<ProfileNavKey.Create> and entry<ProfileNavKey.Edit> (keep symbols
ProfileScreen, LocalNavigator.current, navigateToHome, onBack and the two
entry<> declarations as the call sites).

In
`@Prezel/feature/profile/impl/src/main/java/com/team/prezel/feature/profile/impl/ProfileScreen.kt`:
- Around line 99-116: 현재 ProfileScreen에서 uiState가 Loading일 때 fetchedState가 null로
처리되어 빈 값이 화면에 렌더링됩니다; ProfileScreen에서 uiState (ProfileUiState) 를 분기해
ProfileUiState.Loading일 경우 스피너 또는 스켈레톤을 렌더하도록 추가하고, 기존 ProfileScreenContent 호출은
ProfileUiState.Fetched인 경우에만 fetchedState 값을 전달하도록 변경하세요; 관련 심볼: ProfileScreen,
ProfileUiState, fetchedState, ProfileScreenContent, ProfileScreenTopAppBar —
Loading 분기에서 적절한 로딩 컴포저블을 표시하거나 ProfileScreenContent에 isLoading 플래그를 전달해 내부에서 로딩
UI를 보여주게 구현하면 됩니다.
- Around line 53-69: Split the current single LaunchedEffect into two focused
effects: one LaunchedEffect(Unit) that only dispatches
viewModel.onIntent(ProfileUiIntent.FetchData), and a separate
LaunchedEffect(Unit) (or LaunchedEffect(viewModel) as appropriate) that collects
viewModel.uiEffect.collect and handles ProfileUiEffect cases (NavigateToHome,
OnBack, ShowMessage -> resolve ProfileUiMessage to resId and call
snackbarHostState.showPrezelSnackbar). This separates intent sending from effect
collection (improves readability) while keeping the same handlers
(ProfileUiEffect, ProfileUiMessage, snackbarHostState.showPrezelSnackbar,
navigateToHome, onBack).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@Prezel/feature/profile/impl/src/main/java/com/team/prezel/feature/profile/impl/ProfileScreen.kt`:
- Around line 76-85: The current onClickProfileImage handler only launches
photoPickerLauncher when uiState.shouldLaunchPhotoPicker is true and otherwise
calls viewModel.onIntent(ProfileUiIntent.OnProfileImageChanged(profileUrl = ""))
which deletes the image immediately; update this so tapping always opens the
photo picker instead of sending an empty URL (or split delete into a distinct
action), i.e., change the onClickProfileImage logic to always call
photoPickerLauncher.launch(PickVisualMediaRequest(...)) and move deletion to a
separate UI affordance (e.g., a dedicated delete button or long-press) that
dispatches ProfileUiIntent.OnProfileImageChanged(profileUrl = "") via
viewModel.onIntent.

In
`@Prezel/feature/profile/impl/src/main/java/com/team/prezel/feature/profile/impl/ProfileViewModel.kt`:
- Around line 53-60: On fetchUserInfo failure you only send an effect but never
update the UI state, leaving the screen stuck in Loading; in the onFailure block
of fetchUserInfoUseCase() call update the ViewModel state (via updateState) to
reflect a non-loading / error or retry-able state (e.g. set isLoading = false
and set an error flag/message or switch to a ProfileUiState.Error) and still
call
sendEffect(ProfileUiEffect.ShowMessage(ProfileUiMessage.FETCH_USER_INFO_FAILED));
update the onFailure branch to both send the effect and mutate the state so the
UI can render retry controls instead of an empty loading screen.

---

Duplicate comments:
In
`@Prezel/feature/profile/impl/src/main/java/com/team/prezel/feature/profile/impl/ProfileViewModel.kt`:
- Around line 134-151: The submitProfile() always sends
ProfileUiEffect.NavigateToHome regardless of create/edit; add a mode flag (e.g.,
isNewProfile) to the ViewModel state or include it on the submit intent so
submitProfile() can branch: inside submitProfile(), read the mode from
ProfileUiState.Content (or the submit intent) and send
ProfileUiEffect.NavigateToHome when isNewProfile is true, otherwise send
ProfileUiEffect.OnBack for edit; update the ProfileUiState.Content (or the
submit flow) to carry that isNewProfile boolean and use that symbol in
submitProfile() to decide which effect to send.